How to Handle "Out of Memory" Error Message When Deploying a Trigger?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

What is the appropriate way to deal with this error message when deploying a trigger?

{"error":"hook error","err":"{\"code\":\"Out of Memory\",\"message\":\"you’ve exceeded the memory for this source\",\"ts\":\"2026-06-30T13:47:10.061Z\"}","observations":null}

2

while I have you, any feedback on this?

3

@U03EGTE5WC8 can you guys help triage?

4

What is the trigger?

5

google_drive-new-or-modified-files

6

These were the deployment props:

“drive”: “My Drive”,
“changesPageSize”: 500,
“folders”: ,
“watchForPropertiesChanges”: false,
“includeLink”: true,
“perFileInterval”: 5

Later on we had a successful deployment with "changesPageSize": 200 so do you think this was the cause?

7

Yea, the prop itself mentions this:

Lower values reduce the risk of execution timeouts on active drives.
However I think we can remove an unnecessary log from this source which should reduce memory usage.

8

[BUG] Google Drive triggers going OOM · Issue #21300 · PipedreamHQ/pipedream
tracking this here

9

Thank you!